OPRUN-4607: Fix flags passed to test-experimental-e2e#723
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughMakefile edits in ChangesOpenshift Makefile — E2E targets
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 11 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (11 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tmshort The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test openshift-e2e-aws-techpreview |
0c7d0b1 to
7aa1838
Compare
|
/test openshift-e2e-aws-techpreview |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@openshift/Makefile`:
- Around line 47-48: Replace the short-circuit in the Makefile target
test-experimental-e2e (remove the "/bin/true" line) and restore the real
command(s) that run the experimental e2e suite so the target actually executes
tests; ensure the restored command invokes the same test runner used elsewhere
(e.g., the existing e2e script or binary) and passes the corrected flags/ENV
used for experimental runs so CI executes the suite instead of always
succeeding.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: c1ad50ea-2428-4502-86f2-c79d425a54c2
📒 Files selected for processing (1)
openshift/Makefile
7aa1838 to
d36da45
Compare
|
/test openshift-e2e-aws-techpreview |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@openshift/Makefile`:
- Around line 46-49: The Go test command in the Makefile uses the misspelled
flag "-tieout" which should be "-timeout"; update the invocation (the go test
line that includes $(DOWNSTREAM_E2E_FLAGS) and $(DOWNSTREAM_E2E_TIMEOUT)) to use
"-timeout=$(DOWNSTREAM_E2E_TIMEOUT)" so the Go test timeout is applied and the
make test-e2e target no longer fails due to an unknown flag.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 83c75b64-475b-430d-885d-47b1d524fd27
📒 Files selected for processing (1)
openshift/Makefile
d36da45 to
c79c8d7
Compare
|
/test openshift-e2e-aws-techpreview |
c79c8d7 to
e073781
Compare
|
/test openshift-e2e-aws-techpreview |
e073781 to
2687456
Compare
|
/test openshift-e2e-aws-techpreview |
2687456 to
f17a6e4
Compare
|
/test openshift-e2e-aws-techpreview |
1 similar comment
|
/test openshift-e2e-aws-techpreview |
4df1f20 to
c938bcf
Compare
|
/test openshift-e2e-aws-techpreview |
|
/trest openshift-e2e-aws |
c938bcf to
3fbff88
Compare
|
/test openshift-e2e-aws-techpreview |
3fbff88 to
c87aca2
Compare
- Replace broken test-experimental-e2e target (test/experimental-e2e no longer exists) with /bin/true so triggered jobs always succeed - Pass -timeout=60m to go test; the previous invocation relied on Go's 10m default which is too short for BoxcutterRuntime clusters - Set E2E_STEP_TIMEOUT=15m; BoxcutterRuntime applies resources through sequential phases (CRD must reach Established before the deploy phase starts), making installations slower than the upstream 5m default - Skip ~@CatalogdHA scenarios (require multiple catalogd replicas not present in standard topology) - Skip ~@ProgressDeadline scenarios (require progressDeadlineMinutes < 10 but the OpenShift CRD enforces a minimum of 10) - Skip ~@httpproxy scenarios (too disruptive to cluster networking) Co-Authored-By: Claude Sonnet 4.6 <[email protected]> Signed-off-by: Todd Short <[email protected]>
c87aca2 to
d1f5659
Compare
|
@tmshort: This pull request references OPRUN-4607 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/lgtm |
|
@tmshort: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/verified by @dtfranz |
|
@dtfranz: The DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
UPSTREAM: : Fix downstream e2e test invocation
longer exists) with /bin/true so triggered jobs always succeed
10m default which is too short for BoxcutterRuntime clusters
sequential phases (CRD must reach Established before the deploy phase
starts), making installations slower than the upstream 5m default
present in standard topology)
but the OpenShift CRD enforces a minimum of 10)
Summary by CodeRabbit